Enriched calling based call type notification

ABSTRACT

Systems, methods and apparatuses for implementing enriched calling services for devices may include a first User Equipment (UE) that sends a call request to an IP Multimedia Subsystem (IMS) Core network and a presence server. The IMS core network may determine that the first UE supports enriched calling services and may enable the first UE to perform an enriched calling operation. The IMS core network may forward the call request to a terminating device, such as a second UE and/or a computing device, with the enriched calling operation.

BACKGROUND

In IP Multimedia Subsystems (IMS), a device (e.g., user equipment,herein referred to as a UE) may be capable of enriched calling thatallows the IMS to determine additional information associated with theUE, and/or with a call session being attempted by the UE. With theproliferation of UEs and their enriched calling capabilities, it becomesincreasingly important to efficiently determine which UEs and systemsare enriched calling compatible, what additional information is includedin a request to make an enriched call, and what action to take based onthe additional information.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items.

FIG. 1 depicts an example environment in which systems, methods, andapparatuses may implement enriched calling determination for devices.

FIG. 2 depicts a schematic diagram of a device capabilities databasestored in a presence server, which may form a portion of the systems,methods, and apparatuses of FIG. 1.

FIG. 3 depicts a call flow diagram illustrating example interactions ofthe systems, methods, and apparatuses of FIG. 1 during one or moreenriched calling processes.

FIG. 4 depicts an example enriched calling graphical user interface(GUI) during one or more enriched calling processes.

FIG. 5 depicts a call flow diagram illustrating example interactions ofthe systems, methods, and apparatuses of FIG. 1 during one or moreenriched calling processes.

FIG. 6 depicts an example enriched calling graphical user interface(GUI) during one or more enriched calling processes.

FIG. 7 depicts an example architecture of a computing device configuredto enable one or more enriched calling processes.

FIG. 8 depicts an example architecture of a user equipment (UE)configured to enable one or more enriched calling processes.

FIG. 9 depicts an example process for enabling enriched calling serviceson a UE.

FIG. 10 depicts another example process for enabling enriched callingservices on a UE.

FIG. 11 depicts another example process for enabling enriched callingservices on a UE.

DETAILED DESCRIPTION

Overview

This disclosure is directed to systems, methods and apparatuses forimplementing enriched calling services for devices (hereinafter referredto as “the system”). The system may include an IP Media Subsystem (IMS)core network environment with multiple User Equipments (UE)communicating via device and application communication features. Themultiple UEs may comprise a mix of various hardware manufacturers andmodels, various operating systems of different versions, and variousapplications of different versions operating on the devices.Accordingly, The IMS core network may determine additional informationassociated with a UE or a UE attempting to make a call and use theadditional information to take an action.

In some examples, the system may comprise a UE that is attempting toplace a call to an entity that utilizes Speech Interactive VoiceResponse (SIVR) and/or an Automated Attendant (AA). Historically, SIVRand/or an AA requires voice input from the user making the call orrequire that the user press keys to navigate a call tree. Such methodsmay provide the user with a poor quality-of-experience and/or cause theuser to be on the call for longer than necessary, resulting inadditional resources being used in the system. For an entity that mayreceive thousands of calls a day, it is of the up most importance tohave the user quickly connected with the sub-entity (e.g., billingdepartment, service plan department, account information department,etc.) that the user is attempting to communicate with.

In some examples, the system may receive a call request from the UE. Thecall request may include a telephone number that is associated with anentity that operates a SIVR, an AA, a call tree, or the like. In somecases, the system may determine that the telephone number is a publiclyfacing phone number for an entity (e.g., business) that includesmultiple sub-entities (e.g., departments of the business) and that eachsub-entity is associated with a sub-entity telephone number that isdifferent than the telephone number received from the call request.

In some examples, the system may determine that the UE has enrichedcalling capabilities. For example, call request may include identifyinginformation associated with the UE (e.g., Mobile Station InternationalSubscriber Directory Number (MSISDN) values, etc.) and the system maystore information associated with the UE, such as whether or not the UEhas enriched calling capabilities. In some examples, the call requestmay include an indication that the UE has enriched calling capabilitiesand the system may determine that the UE has enriched callingcapabilities based on the call request.

In some examples, the system may determine that the call requestincludes a subject line in response to determining that the UE hasenriched call capabilities. For example, once the system determines thatthe UE has enriched call capabilities, the system may cause the UE topresent a subject line field that allows the user to enter a subjectassociated with the call. In some cases, the UE may present the subjectline field automatically when the user is making a call.

In some examples, the system may parse words from the subject line anddetermine each word in the subject line. For example, the system maystore a list of words and a list of sub-entities that each correspond toa respective word. For instance, the system may receive a subject linereading “why is my bill so high?” and parse out the individual wordsfrom the subject line. The system may determine a sub-entity associatedwith one of the parsed-out words, such as a billing department beingassociated with the word “bill.”

In some examples, once the system determines that the UE has enrichedcalling capabilities, the system may determine a call type associatedwith the call request. For example, historically, when a terminatingdevice is receiving an incoming call, the terminating device does notinform the user whether the incoming call is a conference call involvingmultiple individuals or is a singular call involving only the userassociated with the incoming call telephone number. This may result inan unpleasant surprise for a user answering an incoming call who doesnot wish to be included in the conference call.

In some examples, the system may determine a call type (e.g., conferencecall, group call, AdHoc conference call, singular call) associated withthe call request and provide an indicator to the terminating devicealong with the call that indicates the call type, thereby allowing theuser of the terminating device to decline a call if the call typeindicates a situation that they do not wish to be involved in.

Multiple and varied example implementations and embodiments aredescribed throughout this disclosure. Examples and portions of thesystems, methods, and apparatuses discussed herein may be rearranged,combined, used together, duplicated, partially omitted, omittedentirely, and/or may be otherwise modified to arrive at variations onthe disclosed implementations that combine one or more aspects of thesystems, methods, and apparatuses.

Illustrative Systems, Methods, and Apparatuses for Implementing EnrichedCalling Capability Determination

FIG. 1 depicts an example system 100 for enriched calling capabilitydetermination with devices. The system 100 may include a first UE 102(A)that communicates with a presence server 104 and is in communicationwith an IMS core network 106. The first UE 102(A) may communicate withthe presence server 104 via the IMS core 106. The first UE 102(A) maysend a subscribe message including information about the first UE102(A), which the presence server 104 may store in a device capabilitiesdatabase 108 upon receiving the subscribe message. In some cases, thepresence server 104 may send an acknowledgement to the first UE 102(A)to confirm that the subscribe message was received, and/or thatinformation from the subscribe message has been extracted and stored inthe device capabilities database 108.

In some examples, the presence server 104 may comprise a server devicethat receives, stores, and sends presence information associated withone or more UEs. For instance, the presence information may comprise oneor more status indicators that convey capabilities and/or availabilityof the one or more UEs for communicating with other one or more UEs. Thepresence server 104 may communicate with a telephony application server(TAS) 110 and/or other nodes of the IMS core network 106 in order tofacilitate receiving and sending the presence information. In somecases, the UE 102(B) may communicate with the presence server 104 andmay inform the presence server 104 of the capabilities associated withthe UE 102(B). For example, the UE 102(B) may send a SIP PUBLISH messageand/or a SIP OPTIONS message to the presence server 104, the IMS corenetwork 106, and/or the TAS 110.

In some embodiments, the first UE 102(A) may comprise a cell phone, asmartphone, a smart watch, a laptop computer, a desktop computer, asmart home device, a tablet device, an Internet-of-Things device, orother types of devices or mobile devices that communicate via the IMScore network 106. In some instances, the first UE 102(A) may comprise adevice identifier that is unique to the particular first UE 102(A). Thedevice identifier may comprise a universally unique identifier (UUID),an International Mobile Equipment Identity (IMEI), or even an absence ofan identifier value which, in some examples, may be associated with aparticular type of device (e.g., iPhone®) and may, therefore, functionas a device identifier by default. In some examples, the first UE 102(A)may be associated with a subscriber number, such as an MSISDN value. Thefirst UE 102(A) may be associated with a single MSISDN value or withmultiple MSISDN values. The MSISDN value associated with the first UE102(A) may change over time and/or may be associated with other UEs. Insome instances, the device identifier and/or the MSISDN value maycomprise information stored at and/or extracted from a subscriberidentity module (SIM) card of the first UE 102(A). In some cases, thefirst UE 102(A) may utilize Voice over (Vo) LTE and/or Video over (Vi)LTE to communicate with any one of the presence server 104, the IMS corenetwork 106, the TAS 110, and/or any other device within the system 100.In some cases, a VoLTE communication may be sent to the TAS 110 and theTAS 110 may interrogate the presence server 104 to establish acommunication session.

In some embodiments, the TAS 110, the presence server 104, the first UE102(A), and/or other elements of the IMS core network 106 may compriseone or more memory device(s) and/or one or more processor(s). The one ormore memory device(s) may comprise non-transitory computer-readablemedia including, but not limited to, phase change memory (PCM), staticrandom-access memory (SRAM), dynamic random-access memory (DRAM), othertypes of random access memory (RAM), read only memory (ROM),electrically erasable programmable ROM (EEPROM), flash memory or othermemory technology, compact disc ROM (CD-ROM), digital versatile discs(DVD) or other optical storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, a quantum-statestorage device, genetic encoding storage device, or any other mediumthat can be used to store information for access by an electronicdevice.

The one or more processor(s) may comprise a microprocessor, amicrocomputer, a microcontroller, a digital signal processor, a centralprocessing unit (CPU), a graphics processing unit (GPU), a quantumprocessor, etc. Among other capabilities, the one or more processor(s)may operate to fetch and execute computer-readable instructions storedin the one or more memory device(s) to perform the operations disclosedherein.

In some examples, the UE 102(A) may attempt to place a call to an entity(e.g., business) that operates a SIVR, an AA, a call tree, or the like.In some examples, the IMS core network 106 may receive a call requestfrom the UE 102(A). In some cases, the IMS core network 106 maydetermine that the call is directed towards an entity that operates aSIVR, an AA, a call tree, or the like prior to the user placing the callrequest (e.g., before a call button is pressed) or during the callrequest (e.g., after the call button is pressed). The call request maybe a session initiation protocol (SIP) subscribe message and include atelephone number that is associated with an entity that operates a SIVR,an AA, a call tree, or the like, and is associated with the computingdevice 112. In some cases, the IMS core network 106 may determine thatthe telephone number is a publicly facing phone number for an entitythat includes multiple sub-entities and that each sub-entity isassociated with a sub-entity (e.g., department of a business) telephonenumber that is different than the telephone number received from thecall request.

In some examples, the IMS core network 106 may determine that the UE102(A) has enriched calling capabilities. For example, the IMS corenetwork 106 may interrogate the presence server 104 to determinecapabilities associated with the UE 102(B) and to determine if the UE102(B) supports enriched calling capabilities. In some cases, the IMScore network 106 may send the call request to the presence server 104and the presence server 104 may determine whether or not the UE 102(A)has enriched calling capabilities. In some examples, the presence server104 may access the device capabilities database 108 to determine if theUE 102(A) has enriched calling capabilities. In some examples, the callrequest may include an indication that the UE 102(A) has enrichedcalling capabilities and the IMS core network 106 may determine that theUE 102(A) has enriched calling capabilities based on the call request.

In some examples, the IMS core network 106 may determine that the callrequest includes a subject line in response to determining that the UE102(A) has enriched call capabilities. For example, once the presenceserver 104 determines that the UE 102(A) has enriched callingcapabilities, the IMS core network 106 may cause the UE 102(A) topresent a subject line field that allows a user associated with the UE102(A) to enter a subject associated with the call request. In somecases, the UE 102(A) may present the subject line field automaticallywhen the user is making a call. In some cases, the user may enter textinto the subject line via touch input on a text entry system of the UE102(A) or the user may enter text into the subject line via a speech totext system of the UE 102(A).

In some examples, the IMS core network 106 may provide the call requestand the subject line to the TAS 110. The TAS 110 may parse words fromthe subject line and determine each word in the subject line. In somecases, the TAS 110 may send the call request, the subject line, and theindividually parsed words to a computing device 112. The computingdevice 112 may comprise an artificial intelligence component, a mediaresource function (MRF) component, or the like. For example, thecomputing device 112 may store a list of words and a list ofsub-entities that each correspond to a respective word. For instance,the IMS core network 106 may receive a subject line reading “why is mybill so high?” The TAS 110 may parse out the individual words (e.g.,“why,” “is,” “my,” “bill,” “so,” and “high”) from the subject line andsend the parsed words with the call request to the computing device 112.The computing device 112 may determine a sub-entity associated with oneof the parsed-out words, such as a billing department being associatedwith the word “bill.” In some cases, the computing device 112 may assigna weight to each individual word based on a relevancy of the word. Forexample, the word “bill” may be assigned a greater weight than the words“is” and “so.” The weights may be based on a user history (e.g.,previous calls and/or searches associated with a user), word type ofwords in the subject line (e.g., noun, pro-noun, adjective, verb, etc.),or other criteria.

In some examples, once the computing device 112 determines a sub-entityin which the user associated with the UE 102(A) wishes to communicatewith, the computing device 112 may forward the call request to thesub-entity directly. In some cases, the sub-entity may be associatedwith a telephone number that is different than the telephone numberinitially entered into the UE 102(A) and is associated with the callrequest. Thereby preventing the user associated with the UE 102(A) fromhaving to navigate a call tree and/or interact with an SIVR or AA.

In some examples, once the presence server 104 determines that the UE102(A) has enriched calling capabilities, the IMS core network 106 maydetermine a call type associated with the call request. For example, thecall request (e.g., SIP invite) may include a telephone numberassociated with a terminating device, such as UE 102(B). The callrequest may indicate whether the call is a singular call (e.g., aone-on-one call between the UE 102(A) and UE 102(B)) or a group call. Insome cases, a group call may include a number of other UEs and the callrequest may indicate that a call session has already been initiatedbetween the UE 102(A) and the other UEs. In some cases, the group callmay include an AdHoc conference call.

In some examples, the IMS core network 106 may determine if theterminating device, in this case, UE 102(B) supports enriched callingcapabilities. For example, the IMS core network 106 may send the callrequest to the presence server 104 and the presence server 104 maydetermine whether or not the UE 102(B) has enriched callingcapabilities. In some cases, the IMS core network 106 may interrogatethe presence server 104 to determine capabilities associated with the UE102(B) and to determine if the UE 102(B) supports enriched callingcapabilities. In some examples, the presence server 104 may access thedevice capabilities database 108 to determine if the UE 102(B) hasenriched calling capabilities.

In some examples, the IMS core network 106 may determine a call type(e.g., conference call, group call, singular call) associated with thecall request and provide the call request as well as an indicator of thecall type to the UE 102(B), thereby allowing the user of the UE 102(B)to decline a call if the call type indicates a situation that they donot wish to be involved in. In some cases, the TAS 110 may determine acall type (e.g., conference call, group call, singular call) associatedwith the call request and provide the call request as well as anindicator of the call type to the UE 102(B). For example, the IMS corenetwork 106 and/or the TAS 110 may prepend into a subject fieldassociated with the call request a call identifier string (e.g.,“conference,” “individual,” etc.) such that when the UE 102(B) receivesthe call request, the UE 102(B) can identify the call type based on thecall identifier string in the subject field.

Multiple and varied example implementations and embodiments aredescribed throughout this disclosure. Examples and portions of thesystems, methods, and apparatuses discussed herein may be rearranged,combined, used together, duplicated, partially omitted, omittedentirely, and/or may be otherwise modified to arrive at variations onthe disclosed implementations that combine one or more aspects of thesystems, methods, and apparatuses.

FIG. 2 depicts a schematic diagram of UE devices communicating with thepresence server 104. For instance, a system 200 (which may be similar oridentical to the system 100) may include a first UE 202(A). UE 202(A)may communicate with the presence server 104, as discussed in greaterdetail below regarding FIGS. 3 and 5.

In some examples, UE 202(A) may comprise a first device identifier204(A) comprising a first device identifier type (e.g., IMEI) and afirst device identifier value (e.g., “1001”) which is particular to theUE 202(A) device, and in some instances may indicate a model and/ormanufacturer of UE 202(A). UE 202(A) may include a first MSISDN value206(A) (e.g., “ABCD”) stored in a memory of UE 202(A) that indicates asubscriber of UE 202(A). UE 202(A) may store a first set of one or moredevice capability indicators 208(A) in memory. For instance, UE 202(A)may comprise a rich communication services (RCS)-enabled device viahardware and software embedded in the device by the manufacturer toexecute RCS applications. As an RCS-enabled device, UE 202(A) may storevarious RCS-based messaging enhancement features, including capabilityindicators to share with other RCS-enabled devices communicating via theRCS applications. For example, UE 202(A) may store the first set of oneor more device capability indicators 208(A) such as a group chatindicator, a File Transfer over Hypertext Transfer Protocol (FTHTTP)capability (e.g., file transfer of 100 MB) indicator, and/or an enrichedcalling capability indicator. UE 202(A) may store a Universal Profile(UP) capability indicator, an RCS capability indicator, and/or UP andRCS capabilities may be derived from other capability indicatorsrepresenting capabilities that are included in the RCS or UP suites ofservices (e.g., group chat and FTHTTP).

In some embodiments, the presence server 104 may store the devicecapabilities database 108 in a memory storage device 210, which maycomprise any of the memory devices discussed above. The memory storagedevice 210 may be located at a same physical node as other components ofthe presence server 104, at a different physical node, or combinationsthereof.

The device capabilities database 108 may comprise one or more of a commadelimited list, a spreadsheet, an array, a NoSQL data structure, ahash-based data structure, an object-based data structure, or any otherdata type, data structure, and/or data system for storing retrievabledata in memory. In some examples, the device capabilities database 108may comprise a spreadsheet with at least a first column for storing oneor more device identifier values, a second column for storing one ormore MSISND values, and a third column for storing one or more sets ofone or more device capability indicators or tuples. A row of thespreadsheet may correspond to a particular device, as represented by thedevice identifier value of the first column in the row, and the othervalues of the row may be associated with the device identifier valueand/or with each other.

For instance, the first example row illustrated in FIG. 2 includes oneor more values that may be associated with the first UE 202(A), such asa device identifier of “IMEI: 1001” indicating the device identifiertype of IMEI and the device identifier value of “1001.” The secondcolumn of the first row includes the MSISDN value “ABCD,” and the thirdcolumn of the first row may include a set of one or more devicecapability indicator values including “group chat;” “FTHTTP;” “enrichedcalling;” “UP;” and/or “RCS.” Accordingly, the presence server 104 maydetermine, based on the values stored in the first row, that the device(e.g., UE 202(A)) associated with the device identifier “IMEI: 1001” isassociated with the MSISDN value “ABCD” and the device capabilityindicators of “group chat;” “FTHTTP;” “enriched calling;” “UP;” and“RCS.”

FIG. 3 depicts a call flow diagram illustrating example interactions ofthe systems disclosed herein during an enriched calling determinationprocess. For instance, a system 300 (which may be similar or identicalto the system(s) 100 and/or 200) may include first UE 202(A) incommunication with the presence server 104 via the IMS core network 106,the TAS server 110, and the computing device 112.

In some examples, the interactions of system 300 may include a phonenumber 302 entered into the UE 202(A) by a user 304. The phone number302 may be a publicly facing phone number associated with an entity thatutilizes SIVR, an AA, a call tree, or the like. In some cases, the UE202(A) may perform a capability discovery 306 to determine if the UE202(A) supports enriched calling. In some cases, if the UE 202(A) doessupport enriched calling, the UE 202(A) may provide an option to theuser 304 via an interface of UE 202(A) to enter a subject line to beassociated with the phone number 302.

In some embodiments, in response to receiving the phone number 302, theUE 202(A) may generate and/or send a subscribe message 308 to thepresence server 104 via the IMS core network 106. In some cases, the IMScore network 106 may forward the subscribe message 308 to the presenceserver 104 as subscribe message 310.

In some embodiments, the subscribe message 308 and/or the subscribemessage 310 may comprise a Session Initiation Protocol (SIP) messagewith a body and a header. In some examples, the header may comprise thedevice identifier type (e.g., IMEI or UUID) and/or device identifiervalue associated with the UE 202(A). The header or the body may comprisethe MSISDN value associated with the UE 202(A). The body may contain theset of one or more capability indicators associated with the UE 202(A).

In some embodiments, the presence server 104 may extract the deviceidentifier type, the device identifier value, the MSISDN value, and/orthe set of one or more capability indicators from the subscribe message308 and/or the subscribe message 310, for instance, to create a dataentry in the device capabilities database 110.

In some embodiments, in response to receiving the subscribe message 310,the presence server 104 may determine a phone number type 312 associatedwith the phone number 302. For example, the presence server 104 maydetermine that the phone number 302 is associated with an entity thatutilizes SIVR, an AA, a call tree, or the like.

In some embodiments, in response to receiving the subscribe message 310,the presence server 104 may perform capability discovery 314 todetermine that the entity associated with the phone number type 312supports enriched calling capabilities.

In some embodiments, in response to determining that that the phonenumber 302 is associated with an entity that utilizes SIVR, an AA, acall tree, or the like, and that the entity associated with the phonenumber 302 supports enriched calling capabilities, the presence server104 may send a notify message 316 to the IMS core network 106 indicatingthat the phone number 302 is associated with an entity that utilizesSIVR, an AA, a call tree, or the like, and that the entity associatedwith the phone number 302 supports enriched calling capabilities. TheIMS core network 106 may forward the notify message 316 to the UE 202(A)as notify message 318.

In some embodiments, in response to receiving the notify message 318,the UE 202(A) may perform capability discovery 320 to determine that theentity associated with the phone number 302 supports enriched callingand may present a subject line field on the interface of the UE 202(A).

In some embodiments, the UE 202(A) may receive a subject 322 from theuser 304 via the subject line field presented on the interface of the UE202(A).

In some embodiments, the UE 202(A) may send an invite message 324 thatincludes the subject 322 to the IMS core network 106. The IMS corenetwork 106 may forward the invite message 324 to the TAS 110 as invitemessage 326.

In some embodiments, the TAS 110 may perform a parse 328 of the subjectincluded in the invite message 326. For example, The TAS 110 may parsewords from the subject line and determine each word in the subject line.

In some embodiments, the TAS 110 may send call request 330 to thecomputing device 112. The call request 330 may include the subject lineand the individually parsed words to a computing device 112. Thecomputing device 112 may comprise an artificial intelligence component,a media resource function (MRF) component, or the like. For example, thecomputing device 112 may store a list of words and a list ofsub-entities that each correspond to a respective word. For instance,the subject 322 may read “why is my bill so high?” The TAS 110 may parseout the individual words at 328 and send the words (e.g., “why,” “is,”“my,” “bill,” “so,” and “high”) in the call request 330 to the computingdevice 112. The computing device 112 may determine a sub-entityassociated with one of the parsed-out words, such as a billingdepartment being associated with the word “bill.”

In some examples, once the computing device 112 determines a sub-entityin which the user associated with the UE 202(A) wishes to communicatewith, the computing device 112 may forward the call request 330 to thesub-entity directly. In some cases, the sub-entity may be associatedwith a telephone number that is different than the telephone numberinitially entered into the UE 202(A) and is associated with the callrequest. Thereby preventing the user associated with the UE 202(A) fromhaving to navigate a call tree and/or interact with an SIVR or AA. Insome cases, the computing device 112 is associated with entityassociated with the phone number 302.

FIG. 4 illustrates an example graphical user interface (GUI) 400 toenable enriched calling functions as described herein. The GUI 400 caninclude, for example, a subject line field 402. The subject line field402 may enable a user to enter in a subject to be associated with anoutgoing call. As illustrated in FIG. 4, the user may enter in a subjectreading “Why is my bill so high?” In this case, if the user is calling acompany to inquire about a service bill, by entering the subject “Why ismy bill so high?”, the call may be automatically directed to thecompanies billing department, which may have a phone number that is notmade publicly available.

The GUI 400 may also include a number input 404. The number input 404can comprise virtual buttons on a touchscreen, physical buttons (e.g.,the user can press a number or letter on a keyboard or keypad), voicecommands, or any other kind of input to enable the user to make theappropriate selection.

FIG. 5 depicts a call flow diagram illustrating example interactions ofthe systems disclosed herein during an enriched calling determinationprocess. For instance, a system 500 (which may be similar or identicalto the system(s) 100 and/or 200) may include first UE 202(A) incommunication with the presence server 104 via the IMS core network 106,the TAS server 110, and the UE 102(B).

In some examples, the interactions of system 500 may include a phonenumber 502 entered into the UE 202(A) by a user 504. The phone number502 may be associated with another UE, such as UE 102(B). In some cases,the UE 202(A) may perform a capability discovery 506 to determine if theUE 202(A) supports enriched calling. In some cases, if the UE 202(A)does support enriched calling, the UE 202(A) may include an indicationthat the UE 202(A) supports enriched calling when sending messages tothe IMS core network 106.

In some embodiments, in response to receiving the phone number 502, theUE 202(A) may generate and/or send a subscribe message 508 to thepresence server 104 via the IMS core network 106. In some cases, the IMScore network 106 may forward the subscribe message 508 to the presenceserver 104 as subscribe message 510.

In some embodiments, the subscribe message 508 and/or the subscribemessage 510 may comprise a Session Initiation Protocol (SIP) messagewith a body and a header. In some examples, the header may comprise thedevice identifier type (e.g., IMEI or UUID) and/or device identifiervalue associated with the UE 202(A). The header or the body may comprisethe MSISDN value associated with the UE 202(A). The body may contain theset of one or more capability indicators associated with the UE 202(A).

In some embodiments, the presence server 104 may extract the deviceidentifier type, the device identifier value, the MSISDN value, and/orthe set of one or more capability indicators from the subscribe message508 and/or the subscribe message 510, for instance, to create a dataentry in the device capabilities database 110.

In some embodiments, in response to receiving the subscribe message 510,the presence server 104 may perform capability discovery 512 todetermine that the entity associated with the phone number 502 supportsenriched calling capabilities.

In some embodiments, in response to determining that the entityassociated with the phone number 302 supports enriched callingcapabilities, the presence server 104 may send a notify message 514 tothe IMS core network 106 indicating that the entity associated with thephone number 302 supports enriched calling capabilities. The IMS corenetwork 106 may forward the notify message 514 to the UE 202(A) asnotify message 516.

In some embodiments, in response to receiving the notify message 516,the UE 202(A) may perform capability discovery 518 to determine that theentity associated with the phone number 502 supports enriched callingand may determine a call type (e.g., conference call, group call,singular call) associated with the call request. In some cases, a groupcall may include a number of other UEs and the UE 202(A) may determinethat a call session has already been initiated between the UE 202(A) andthe other UEs.

In some embodiments, the UE 202(A) may send an invite message 520 thatincludes the call type to the IMS core network 106. The IMS core network106 may forward the invite message 520 to the TAS 110 as invite message522.

In some embodiments, the TAS 110 may perform a call type determination524 in order to determine a call type associated with the call request.In some cases, the TAS 110 may determine a number of other UEsparticipating in an ongoing call session that is associated with theinvite message 522.

In some embodiments, the TAS 110 may send call request 526 to the UE102(B). The call request 526 may include an indication of the call typeassociated with the call request 526. In some cases, the call request526 may cause the UE 102(B) to present an indication of the call type(e.g., conference call, group call, singular call) associated with thecall request so that a user associated with the UE 102(B) may beinformed of the type of call that they will be involved in if the callis answered.

FIG. 6 illustrates an example graphical user interface (GUI) 600 toenable enriched calling functions as described herein. The GUI 600 caninclude, for example, a call type indicator 602. The call type indicatormay enable a user to determine if the incoming call is with anindividual or is a group call. As illustrated in FIG. 6, the GUI 600 maypresent an incoming call from “CALLER A” and may present an “Individual”indicator 604 and a “Group Call” indicator 606. In this case, inresponse to the incoming call being from an individual, an indicator 608may be presented next to the “Individual” indicator 604. Although, inthe example of FIG. 6, the indicator 608 is illustrated as a checkmark,it is to be understood that any symbol may be used to indicate whichtype of call the incoming is determined to be. In some cases, noindicator may be used, and the GUI 600 may simply present either one ofthe “Individual” indicator 604 or the “Group Call” indicator 606 basedon the call type.

The GUI 600 may also include an answer button 610 and a decline button612 to enable the user associated with the UE 102(B) to answer ordecline the incoming call. The answer button 610 and the decline button612 can comprise virtual buttons on a touchscreen, physical buttons(e.g., the user can press a number or letter on a keyboard or keypad),voice commands, or any other kind of input to enable the user to makethe appropriate selection.

FIG. 7 illustrates an example computing device 700 that may berepresentative of the TAS 110, the computing device 112, or acombination thereof, as discussed herein. The computing device 700 cancomprise a number of components to execute part, or all, of theabove-mentioned systems and methods. The computing device 700 cancomprise memory 702 including, for example, an OS 704, a parsingcomponent 706, a subject determination component 708, and a call typedetermination component 710. In various implementations, the memory 702can be volatile (such as RAM), non-volatile (such as ROM, flash memory,etc.), or some combination of the two. The memory 702 can include all,or part, of the OS 704, the parsing component 706, the subjectdetermination component 708, and the call type determination component710 for the computing device 700, among other things.

The OS 704 can vary depending on the manufacturer of the computingdevice 700 and the type of component. Many servers, for example, runLinux or Windows server. Dedicated cellular routing servers may runspecific telecommunications OSs. The OS 704 contains the modules andsoftware that supports a computer's basic functions, such as schedulingtasks, executing applications, and controlling peripherals. The OS 704can enable the computing device 700 to send and receive SIP messages,connect with UEs, provide audio and/or video playback, etc. Thus, the OS704 can also enable the computing device 700 to perform some, or all, ofthe functions associated with the systems and methods discussed herein.

In some examples, the memory 702 can also include the parsing component706. The parsing component 706 can enable the computing device 700 toparse words included in a subject line that is included in a callrequest (e.g., SIP Invite). For example, the parsing component 706 mayparse words from the subject line and determine each word in the subjectline.

In some examples, the memory 702 can also include the subjectdetermination component 708. For example, the subject determinationcomponent 708 may store a list of words and a list of sub-entities thateach correspond to a respective word. For instance, the subject line mayread “why is my bill so high?” The parsing component 706 may parse outthe individual words and send the words (e.g., “why,” “is,” “my,”“bill,” “so,” and “high”) the subject determination component 708. Thesubject determination component 708 may determine a sub-entityassociated with one of the parsed-out words, such as a billingdepartment being associated with the word “bill.”

In some examples, the memory 702 can also include the call typedetermination component 710. The call type determination component 710may determine a call type associated with a call request. In some cases,the call type determination component 710 may determine a number ofother UEs participating in an ongoing call session that is associatedwith an invite message.

The computing device 700 can also comprise one or more processors 712.In some implementations, the processor(s) 712 can be a centralprocessing unit (CPU), a graphics processing unit (GPU), both CPU andGPU, or any other processing unit. The computing device 700 can alsoinclude one or more of removable storage 714, non-removable storage 716,transceiver(s) 718, output device(s) 720, and input device(s) 722.

The computing device 700 may also include additional data storagedevices (removable and/or non-removable) such as, for example, magneticdisks, optical disks, or tape. Such additional storage is illustrated inFIG. 7 by removable storage 714 and non-removable storage 716. Theremovable storage 714 and non-removable storage 716 can store some, orall, of the OS 704, the parsing component 706, the subject determinationcomponent 708, and the call type determination component 710.

Non-transitory computer-readable media may include volatile andnonvolatile, removable and non-removable tangible, physical mediaimplemented in technology for storage of information, such ascomputer-readable instructions, data structures, program modules, orother data. The memory 702, removable storage 714, and non-removablestorage 716 are all examples of non-transitory computer-readable media.Non-transitory computer-readable media include, but are not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, DVDsor other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other tangible,physical medium which can be used to store the desired information andwhich can be accessed by the computing device 700. Any suchnon-transitory computer-readable media may be part of the computingdevice 700 or may be a separate database, databank, remote server, orcloud-based server.

In some implementations, the transceiver(s) 718 include any transceiversknown in the art. In some examples, the transceiver(s) 718 can includewireless modem(s) to facilitate wireless connectivity with multiple UEs,the Internet, the cellular network, and/or an intranet via a cellularconnection. The transceiver(s) 718 may enable the computing device 700to connect with the UEs on multiple networks (e.g., 2G, 3G, 4G, and 5Gnetworks). The transceiver(s) 718 can comprise multiple single frequencytransceivers or one or more multi-frequency/multi-channel transceiversto enable the computing device 700 to communicate with tens, hundreds,or even thousands of UEs simultaneously.

The transceiver(s) 718 may include a radio transceiver that performs thefunction of transmitting and receiving radio frequency communicationsvia an antenna (e.g., Wi-Fi or Bluetooth®) to connect to an IP corenetwork or another network. In other examples, the transceiver(s) 718may include wired communication components, such as a wired modem orEthernet port.

In some implementations, the output device(s) 720 include any outputdevices known in the art, such as a display (e.g., a liquid crystal orthin-film transistor (TFT) display), a touchscreen display, speakers, avibrating mechanism, or a tactile feedback mechanism. In some examples,the output device(s) 720 can play various sounds based on, for example,when a UE is connected or disconnected, when a video or audio streamstarts or stops, when a transfer is declined, etc. Output device(s) 720can also include ports for one or more peripheral devices, such asheadphones, peripheral speakers, or a peripheral display.

In various implementations, input device(s) 722 include any inputdevices known in the art. For example, the input device(s) 722 mayinclude a camera, a microphone, a keyboard/keypad, or a touch-sensitivedisplay. A keyboard/keypad may be a standard push button alphanumeric,multi-key keyboard (such as a conventional QWERTY keyboard), virtualcontrols on a touchscreen, or one or more other types of keys orbuttons, and may also include a joystick, wheel, and/or designatednavigation buttons, or the like.

FIG. 8 depicts a component level view of a UE 800 (e.g., UE 102(A)and/or UE 102(B) for use with the systems and methods described herein.The UE 800 could be any UE capable of making audio and/or video calls ona cellular network, the IMS core network 106, and the like. For clarity,the UE 800 is described herein generally as a cell phone, smart phone,or laptop computer. One of skill in the art will recognize, however,that the systems and methods described herein can also be used with avariety of other electronic devices, such as, for example, tabletcomputers, desktops, and other network (e.g., cellular or IP network)connected devices. Indeed, the UE 800 can be any device that can sendand receive video and/or audio calls that can benefit from improved callmanagement.

The UE 800 can comprise several components to execute theabove-mentioned functions. As discussed below, the UE 800 can comprisememory 802 including an operating system (OS) 804 and one or morestandard applications 806. The standard applications 806 can includemany features common to UE 800 such as, for example, calendars, calllogs, voicemail, etc. In this case, the standard applications 806 canalso comprise a video call application (e.g., Facetime®, Zoom®, GoogleHangouts®, Skype®, etc.) and a standard audio call application to enableusers to engage in audio and video calls, as described above. Thestandard applications 806 can also include contacts to enable the userto select a contact to initiate a video call and/or to select a transfertarget.

The UE 800 can also comprise a subject line GUI 808 and a call type GUI810. The subject line GUI 808 and the call type GUI 810 can be used inconjunction with the enriched calling capabilities of the UE 800 toenable the UE 800 to provide enriched calling features, such haspresenting GUI 400 and/or GUI 600.

The UE 800 can also comprise one or more processors 812 and one or moreof removable storage 814, non-removable storage 816, transceiver(s) 818,output device(s) 820, and input device(s) 822. In some examples, such asfor cellular communication devices, the UE 800 can also include asubscriber identity module (SIM) 824 and/or an embedded SIM (eSIM) 826,which can include a mobile country code (MCC), mobile network code(MNC), international mobile subscriber identity (IMSI), and otherrelevant information. In some examples, one or more of the functions(e.g., standard applications 806 and/or subject the line GUI 808 and thecall type GUI 810) can be stored on the SIM 824 or the eSIM 826 inaddition to, or instead of, being stored in the memory 802.

In various implementations, the memory 802 can be volatile (such asrandom access memory (RAM)), non-volatile (such as read only memory(ROM), flash memory, etc.), or some combination of the two. The memory802 can include all, or part, of the OS 804, applications 806, thesubject line GUI 808, and the call type GUI 810, for the UE 800, amongother things. In some examples, rather than being stored in the memory802, some, or all, of the OS 804, applications 806, the subject line GUI808, and the call type GUI 810 and other information (e.g., callhistory, contacts, etc.) can be stored on a remote server or a cloud ofservers accessible by the UE 800 such as the IMS core network 106 and/orthe TAS 110.

The memory 802 can also include the OS 804. Of course, the OS 804 variesdepending on the manufacturer of the UE 800 and currently comprises, forexample, iOS 11.4.1 for Apple products and Pie for Android products. TheOS 804 contains the modules and software that support a UE's basicfunctions, such as scheduling tasks, executing applications, andcontrolling peripherals. In some examples, the OS 804 can enable thevideo call application to conduct video calls and call transfers, asdescribed above, via the transceiver(s) 818. The OS 804 can sendinformation to the subject line GUI 808 and the call type GUI 810, forexample, to cause the subject line GUI 808 and the call type GUI 810 todisplay contact information, phone numbers, and other call data. The OS804 can also receive inputs from the subject line GUI 808 and the calltype GUI 810 to cause the transceiver to send data, for example, or tochange a display on the UE 800, among other things. The OS 804 can alsoenable the UE 800 to send and retrieve other data via a cellular dataconnection or internet connection and perform other functions.

The UE 800 can also comprise one or more processors 812. In someimplementations, the processor(s) 812 can be a central processing unit(CPU), a graphics processing unit (GPU), both CPU and GPU, or any otherprocessing unit. The UE 800 may also include additional data storagedevices (removable and/or non-removable) such as, for example, magneticdisks, optical disks, or tape. Such additional storage is illustrated inFIG. 8 by removable storage 814 and non-removable storage 816. Theremovable storage 814 and non-removable storage 816 can store some, orall, of the OS 804, applications 806, the subject line GUI 808, and thecall type GUI 810.

Non-transitory computer-readable media may include volatile andnonvolatile, removable and non-removable tangible, physical mediaimplemented in technology for storage of information, such as computerreadable instructions, data structures, program modules, or other data.The memory 802, removable storage 814, and non-removable storage 816 areall examples of non-transitory computer-readable media. Non-transitorycomputer-readable media include, but are not limited to, RAM, ROM,electronically erasable programmable ROM (EEPROM), flash memory or othermemory technology, compact disc ROM (CD-ROM), digital versatile discs(DVD) or other optical storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othertangible, physical medium which can be used to store the desiredinformation and which can be accessed by the UE 800. Any suchnon-transitory computer-readable media may be part of the UE 800 or maybe a separate database, databank, remote server, or cloud-based server.

In some implementations, the transceiver(s) 818 include any transceiversknown in the art. In some examples, the transceiver(s) 818 can includewireless modem(s) to facilitate wireless connectivity (e.g. wirelesstransmissions) with other components (e.g., between UEs), the Internet,and/or an intranet via cellular and IP networks. Specifically, thetransceiver(s) 818 can include one or more transceivers 818 that canenable the UE 800 to connect to, and transfer, both video and/or audiocalls. Thus, the transceiver(s) 818 can include multiple single-channeltransceivers 818 or a multi-frequency, multi-channel transceiver 818 toenable the UE 800 to send and receive a bidirectional video stream and abidirectional audio stream, among other things. The transceiver(s) 818can enable the UE 800 to connect to multiple networks including, but notlimited to 2G, 3G, 4G and 5G networks. The transceiver(s) 818 can alsoinclude one or more transceivers 818 to enable the UE 800 to connect tofuture (e.g., 6G) networks, Internet-of-Things (IoT), machine-to machine(M2M), and other current and future networks.

The transceiver(s) 818 may also include one or more radio transceiversthat perform the function of transmitting and receiving radio frequencycommunications via an antenna (e.g., Wi-Fi or Bluetooth®). In otherexamples, the transceiver(s) 818 may include wired communicationcomponents, such as a wired modem or Ethernet port, for communicatingvia one or more wired networks. The transceiver(s) 818 can enable the UE800 to make audio and video calls, download files, access webapplications, and provide other communications associated with thesystems and methods, described above.

In some implementations, the output device(s) 820 include any outputdevices known in the art, such as a display (e.g., a liquid crystal orthin-film transistor (TFT) display), a touchscreen, speakers, avibrating mechanism, or a tactile feedback mechanism. Thus, the outputdevice(s) can include a screen, or display, on which the subject lineGUI 808 and the call type GUI 810 can be displayed. The output device(s)820 can also include speakers, or similar devices, to play sounds orringtone when an audio call, video call, or transferred call is beingreceived. The output device(s) 820 can also provide tones or sounds whena video transfer is complete, for example, or when other tasksassociated with the systems and methods described herein are initiatedor completed. Output device(s) 820 can also include ports for one ormore peripheral devices, such as headphones, peripheral speakers, or aperipheral display.

In various implementations, input device(s) 822 include any inputdevices known in the art. For example, the input device(s) 822 mayinclude a camera, a microphone, or a keyboard/keypad. The inputdevice(s) 822 can include a touch-sensitive display or a keyboard toenable users to enter data and make requests and receive responses viaweb applications (e.g., in a web browser), make audio and video calls,and use the standard applications 808, among other things. Thetouch-sensitive display or keyboard/keypad may be a standard push buttonalphanumeric multi-key keyboard (such as a conventional QWERTYkeyboard), virtual controls on a touchscreen, or one or more other typesof keys or buttons, and may also include a joystick, wheel, and/ordesignated navigation buttons, or the like.

The touch sensitive display can be used to display the subject line GUI808, and the call type GUI 810 and to act as both an input device 822and an output device 820. The touch sensitive display can display thekeypad, for example, to enable the user to enter a subject line on thesubject line GUI 808. Thus, the touch sensitive display can display thesubject line GUI 808 and the call type GUI 810, including relevant callinformation and receive selections from the user (e.g., to answer acall, decline a call, etc.), among other things.

Example Processes

FIGS. 9-11 illustrate example processes. These processes are illustratedas logical flow graphs, each operation of which represents a sequence ofoperations that can be implemented in hardware, software, or acombination thereof. In the context of software, the operationsrepresent computer-executable instructions stored on one or morecomputer readable storage media that, when executed by one or moreprocessors, perform the recited operations. Generally,computer-executable instructions include routines, programs, objects,components, data structures, and the like that perform particularfunctions or implement particular abstract data types. The order inwhich the operations are described is not intended to be construed as alimitation, and any number of the described operations can be omitted,reordered, or combined in any order and/or in parallel to implement theprocesses.

FIG. 9 illustrates an example process 900 for routing a call requestbased at least in part on a subject line associated with the callrequest. As illustrated at 902, a computing device may receive a callrequest from a user equipment (UE). For example, the UE 102(A) mayattempt to place a call to an entity that operates a SIVR, an AA, a calltree, or the like. In some examples, the IMS core network 106 mayreceive a call request from the UE 102(A). The call request may be anSIP subscribe message and include a telephone number that is associatedwith an entity that operates a SIVR, an AA, a call tree, or the like,and is associated with the computing device 112.

At 904, the computing device may determine that the UE has enriched callcapabilities. For example, the IMS core network 106 may send the callrequest to the presence server 104 and the presence server 104 maydetermine whether or not the UE 102(A) has enriched callingcapabilities. In some examples, the presence server 104 may access thedevice capabilities database 108 to determine if the UE 102(A) hasenriched calling capabilities. In some examples, the call request mayinclude an indication that the UE 102(A) has enriched callingcapabilities and the IMS core network 106 may determine that the UE102(A) has enriched calling capabilities based on the call request.

At 906, the computing device may determine that the call requestincludes a subject line in response to determining that the UE hasenriched call capabilities. For example, the presence server 104determines that the UE 102(A) has enriched calling capabilities, the IMScore network 106 may cause the UE 102(A) to present a subject line fieldthat allows a user associated with the UE 102(A) to enter a subjectassociated with the call request. In some cases, the UE 102(A) maypresent the subject line field automatically when the user is making acall.

At 908, the computing device may determine at least one word included inthe subject line. For example, the IMS core network 106 may provide thecall request and the subject line to the TAS 110. The TAS 110 may parsewords from the subject line and determine each word in the subject line.

At 910, the computing device may determine at least one entityassociated with the at least one word. For example, the TAS 110 may sendthe call request, the subject line, and the individually parsed words toa computing device 112. The computing device 112 may comprise anartificial intelligence component, a media resource function (MRF)component, or the like. For example, the computing device 112 may storea list of words and a list of sub-entities that each correspond to arespective word. For instance, the IMS core network 106 may receive asubject line reading “why is my bill so high?” The TAS 110 may parse outthe individual words (e.g., “why,” “is,” “my,” “bill,” “so,” and “high”)from the subject line and send the parsed words with the call request tothe computing device 112. The computing device 112 may determine asub-entity associated with one of the parsed-out words, such as abilling department being associated with the word “bill.”

At 912, the computing device may route the call request to the at leastone entity in response to the at least one entity being associated withthe word. For example, once the computing device 112 determines asub-entity in which the user associated with the UE 102(A) wishes tocommunicate with, the computing device 112 may forward the call requestto the sub-entity directly. In some cases, the sub-entity may beassociated with a telephone number that is different than the telephonenumber initially entered into the UE 102(A) and is associated with thecall request.

FIG. 10 illustrates an example process 1000 for providing a call typeindicator to a terminating device. As illustrated at 1002, a computingdevice may receive a call request from a first user equipment (UE). Forexample,

At 1004, the computing device may determine at least one second UE as arecipient associated with the call request. For example, the callrequest (e.g., SIP invite) may include a telephone number associatedwith a terminating device, such as UE 102(B).

At 1006, the computing device may determine that the second UE hasenriched call capabilities. For example, the IMS core network 106 maysend the call request to the presence server 104 and the presence server104 may determine whether or not the UE 102(B) has enriched callingcapabilities. In some examples, the presence server 104 may access thedevice capabilities database 108 to determine if the UE 102(B) hasenriched calling capabilities.

At 1008, the computing device may determine a call type associated withthe call request. For example, the call request may indicate whether thecall is a singular call (e.g., a one-on-one call between the UE 102(A)and UE 102(B)) or a group call. In some cases, a group call may includea number of other UEs and the call request may indicate that a callsession has already been initiated between the UE 102(A) and the otherUEs.

At 1010, the computing device may send the call request to the secondUE, the call request including an indication of the call type. Forexample, the IMS core network 106 may determine a call type (e.g.,conference call, group call, singular call) associated with the callrequest and provide the call request as well as an indicator of the calltype to the UE 102(B).

FIG. 11 illustrates an example process 1100 for routing a call requestbased at least in part on a subject line associated with the callrequest. As illustrated at 1102, a computing device may receive a callrequest from a telephony application server (TAS) associated with a userequipment (UE), the call request including multiple parsed words of asubject line associated with the call request. For example, the TAS 110may send call request 330 to the computing device 112.

At 1104, the computing device may identify a word from the multipleparsed words. For example, call request 330 may include the subject lineand the individually parsed words to a computing device 112.

At 1106, the computing device may determine that the word is associatedwith at least one sub-entity of an entity. For example, the computingdevice 112 may store a list of words and a list of sub-entities thateach correspond to a respective word. For instance, the subject 322 mayread “why is my bill so high?” The TAS 110 may parse out the individualwords at 328 and send the words (e.g., “why,” “is,” “my,” “bill,” “so,”and “high”) in the call request 330 to the computing device 112. Thecomputing device 112 may determine a sub-entity associated with one ofthe parsed-out words, such as a billing department being associated withthe word “bill.”

At 1108, the computing device may route the call request to the at leastone sub-entity in response to the at least one sub-entity beingassociated with the word. For example, once the computing device 112determines a sub-entity in which the user associated with the UE 202(A)wishes to communicate with, the computing device 112 may forward thecall request 330 to the sub-entity directly. In some cases, thesub-entity may be associated with a telephone number that is differentthan the telephone number initially entered into the UE 202(A) and isassociated with the call request.

Although FIGS. 9-11 illustrate example operations, the describedoperations in these figures (and all other methods and operationsdisclosed herein) may be performed in other orders different than thoseillustrated in FIGS. 9 and 10 and multiple steps may be performedsimultaneously or in parallel. Furthermore, in some embodiments, one ormore operations illustrated in FIGS. 9 and 10 may be omitted, repeated,and/or combined with other operations illustrated in FIGS. 9 and 10, orany other operations and components discussed in this disclosure.

Example Clauses

A: A system comprising: one or more processors; a memory; and one ormore components stored in the memory and executable by the one or moreprocessors to perform operations comprising: receiving a call requestfrom a first user equipment (UE); determining at least one second UE asa recipient associated with the call request; determining that thesecond UE has enriched call capabilities; determining a call typeassociated with the call request; and sending the call request to thesecond UE, the call request including an indication of the call type.

B: The system of claim A, wherein the call request includes a SessionInitiation Protocol (SIP) INVITE and the call type is included in theSIP INVITE.

C: The system of claim A or B, wherein the call type includes at leastone of a conference call or an individual call.

D: The system of claim A-C, wherein the at least one of the first UE orthe second UE is a VoLTE device.

E: The system of claim A-D, wherein the recipient is a first recipientand the call request includes a second recipient.

F: The system of claim A-E, wherein the call type is determined by atelephony application server (TAS) and the operations further comprise,in response to determining the call type associated with the callrequest, adding a call identifier string to a subject field associatedwith the call request.

G: The system of claim A-F, wherein sending the call request to thesecond UE causes the second UE to present a call type indicator on agraphical user interface of the second UE.

H: A method comprising: receiving a call request from a first userequipment (UE); determining at least one second UE as a recipientassociated with the call request; determining that the second UE hasenriched call capabilities; determining a call type associated with thecall request; and sending the call request to the second UE, the callrequest including an indication of the call type.

I: The method of claim H, wherein the call request includes a SessionInitiation Protocol (SIP) INVITE and the call type is included in theSIP INVITE.

J: The method of claim H or I, wherein the call type includes at leastone of a conference call or an individual call.

K: The method of claim H-J, wherein the at least one of the first UE orthe second UE is a VoLTE device.

L: The method of claim H-K, wherein sending the call request to thesecond UE causes the second UE to present a call type indicator on agraphical user interface of the second UE.

M: The method of claim H-L, wherein the recipient is a first recipientand the call request includes a second recipient.

N: The method of claim M, further comprising determining that the calltype is a group call in response to the call request including the firstrecipient and the second recipient.

O: The method of claim H-L, wherein sending the call request to thesecond UE causes the second UE to present a call type indicator on agraphical user interface of the second UE.

P: The method of claim O, wherein the call type indicator includes anidentifier of at least a third UE included in the call request.

Q: A method comprising: receiving a call request from a first userequipment (UE); determining at least one second UE as a recipientassociated with the call request; determining that the second UE hasenriched call capabilities; determining that the call request isassociated with a group call; and sending the call request to the secondUE, the call request including an indication of the call request is agroup call.

R: The method of claim Q, wherein the call request includes a SessionInitiation Protocol (SIP) INVITE and the indication that the callrequest is the group call is included in the SIP INVITE.

S: The method of claim Q or R, wherein the at least one of the first UEor the second UE is a VoLTE device.

T: The method of claim Q-S, wherein sending the call request to thesecond UE causes the second UE to present a call type indicator on agraphical user interface of the second UE.

U: A system comprising: one or more processors; a memory; and one ormore components stored in the memory and executable by the one or moreprocessors to perform operations comprising: receiving a call requestfrom a user equipment (UE); determining that the UE has enriched callcapabilities; determining that the call request includes a subject linein response to determining that the UE has enriched call capabilities;determining at least one word included in the subject line; determiningat least one entity associated with the at least one word; and routingthe call request to the at least one entity in response to the at leastone entity being associated with the at least one word.

V: The system of claim U, wherein the call request includes a SessionInitiation Protocol (SIP) INVITE and the subject line is included in theSIP INVITE.

W: The system of claim U or V, the operations further comprising:determining that the call request includes a telephone number associatedwith an entity type; and causing the UE to display a subject line fieldin response to the telephone number being associated with the entitytype.

X: The system of claim U-W, wherein: the entity type is a business; theat least one entity is a sub-entity of the business; and determining theat least one entity being associated with the at least one word includesselecting the at least one entity from a list of multiple sub-entitiesof the business.

Y: The system of claim U-X, wherein determining the at least one wordincluded in the subject line includes parsing multiple words from thesubject line.

Z: The system of claim Y, the operations further comprising: assigningat least one weight to the at least one word; and determining the atleast one entity associated with the at least one word based at least inpart on the at least one weight.

AA: The system of claim U-X, wherein the call request includes a firsttelephone number and the at least one entity is associated with a secondtelephone number that is different than the first telephone number.

AB: A method comprising: receiving a call request from a user equipment(UE); determining that the UE has enriched call capabilities;determining that the call request includes a subject line in response todetermining that the UE has enriched call capabilities; determining atleast one word included in the subject line; determining at least oneentity associated with the at least one word; and routing the callrequest to the at least one entity in response to the at least oneentity being associated with the at least one word.

AC: The method of claim AB, wherein the call request includes a SessionInitiation Protocol (SIP) INVITE and the subject line is included in theSIP INVITE.

AD: The method of claim AB or AC, further comprising: determining thatthe call request includes a telephone number associated with an entitytype; and causing the UE to display a subject line field in response tothe telephone number being associated with the entity type.

AE: The method of claim AB-AD, wherein: the entity type is a business;the at least one entity is a sub-entity of the business; and determiningthe at least one entity being associated with the at least one wordincludes selecting the at least one entity from a list of multiplesub-entities of the business.

AF: The method of claim AB-AE, wherein determining the at least one wordincluded in the subject line includes parsing multiple words from thesubject line.

AG: The method of claim AF, further comprising: assigning at least oneweight to the at least one word; and determining the at least one entityassociated with the at least one word based at least in part on the atleast one weight.

AH: The method of claim AB-AG, wherein the call request includes a firsttelephone number and the at least one entity is associated with a secondtelephone number that is different than the first telephone number.

AI: The method of claim AB-AH, wherein determining the at least one wordincluded in the subject line includes parsing, by a telephonyapplication server (TAS) the subject line into individual words.

AJ: The method of claim AB-AI, wherein routing the call request to theat least one entity is performed by at least one of an artificialintelligence component or a media resource function (MRF) component.

AK: A system comprising: one or more processors; a memory; and one ormore components stored in the memory and executable by the one or moreprocessors to perform operations comprising: receiving a call requestfrom a telephony application server (TAS) associated with a userequipment (UE), the call request including multiple parsed words of asubject line associated with the call request; identifying a word fromthe multiple parsed words; determining that the word is associated withat least one sub-entity of an entity; and routing the call request tothe at least one sub-entity in response to the at least one sub-entitybeing associated with the word.

AL: The system of claim AK, wherein the call request includes a SessionInitiation Protocol (SIP) INVITE and the subject line is included in theSIP INVITE.

AM: The system of claim AK or AL, wherein: the entity is a business; anddetermining that the word is associated with the at least one sub-entityincludes selecting the at least one sub-entity from a list of multiplesub-entities of the business.

AN: The system of claim AK-AM, the operations further comprising:assigning a weight to each of the multiple parsed words; and determiningthat the word is associated with the at least one sub-entity is based atleast in part on the weight assigned to each of the multiple parsedwords.

While the example clauses described above are described with respect toone particular implementation, it should be understood that, in thecontext of this document, the content of the example clauses can also beimplemented via a method, device, system, computer-readable medium,and/or another implementation. Additionally, any of examples A-AN may beimplemented alone or in combination with any other one or more of theexamples A-AN.

CONCLUSION

Although this disclosure uses language specific to structural featuresand/or methodological acts, it is to be understood that the scope of thedisclosure is not necessarily limited to the specific features or actsdescribed. Rather, the specific features and acts are disclosed asillustrative forms of implementation.

What is claimed is:
 1. A telephony application server (TAS) comprising:one or more processors; a memory; and one or more components stored inthe memory and executable by the one or more processors to performoperations comprising: receiving a call request from a first userequipment (UE); determining at least one second UE as a recipientassociated with the call request; determining that the second UE hasenriched call capabilities; determining a call type associated with thecall request; and in response to determining that the second UE hasenriched call capabilities, sending the call request to the second UE,the call request including an indication of the call type, wherein thecall type is at least one of a conference call or individual call. 2.The TAS of claim 1, wherein the call request includes a SessionInitiation Protocol (SIP) INVITE and the call type is included in theSIP INVITE.
 3. The TAS of claim 1, wherein the at least one of the firstUE or the second UE is a VoLTE device.
 4. The TAS of claim 1, whereinthe recipient is a first recipient and the call request includes asecond recipient.
 5. The TAS of claim 1, wherein the operations furthercomprise, in response to determining the call type associated with thecall request, adding a call identifier string to a subject fieldassociated with the call request.
 6. The TAS of claim 1, wherein sendingthe call request to the second UE causes the second UE to present a calltype indicator on a graphical user interface of the second UE.
 7. Amethod comprising: receiving, by a telephony application server (TAS), acall request from a first user equipment (UE); determining, by the TAS,at least one second UE as a recipient associated with the call request;determining, by the TAS, that the second UE has enriched callcapabilities; determining, by the TAS, a call type associated with thecall request; and in response to determining that the second UE hasenriched call capabilities, sending, by the TAS, the call request to thesecond UE, the call request including an indication of the call type,wherein the call type is at least one of a conference call or individualcall.
 8. The method of claim 7, wherein the call request includes aSession Initiation Protocol (SIP) INVITE and the call type is includedin the SIP INVITE.
 9. The method of claim 7, wherein the at least one ofthe first UE or the second UE is a VoLTE device.
 10. The method of claim7, wherein sending the call request to the second UE causes the secondUE to present a call type indicator on a graphical user interface of thesecond UE.
 11. The method of claim 7, wherein the recipient is a firstrecipient and the call request includes a second recipient.
 12. Themethod of claim 11, further comprising determining that the call type isa group call in response to the call request including the firstrecipient and the second recipient.
 13. The method of claim 7, whereinsending the call request to the second UE causes the second UE topresent a call type indicator on a graphical user interface of thesecond UE.
 14. The method of claim 13, wherein the call type indicatorincludes an identifier of at least a third UE included in the callrequest.
 15. A non-transitory computer-readable medium havingprogramming instructions stored thereon which, when executed by aprocessor associated with a telephony application server (TAS) cause theTAS to perform operations comprising: receiving a call request from afirst user equipment (UE); determining at least one second UE as arecipient associated with the call request; determining that the secondUE has enriched call capabilities; determining a call type associatedwith the call request and in response to determining that the second UEhas enriched call capabilities, sending the call request to the secondUE, the call request including an indication of the call type, whereinthe call type is at least one of a conference call or individual call.16. The non-transitory computer-readable medium of claim 15, wherein thecall request includes a Session Initiation Protocol (SIP) INVITE and theindication of the call type is included in the SIP INVITE.
 17. Thenon-transitory computer-readable medium of claim 15, wherein the atleast one of the first UE or the second UE is a VoLTE device.
 18. Thenon-transitory computer-readable medium of claim 15, wherein sending thecall request to the second UE causes the second UE to present a calltype indicator on a graphical user interface of the second UE.